Software updating system, information processing apparatus and method, recording medium and program

ABSTRACT

It is made possible to update software appropriately. When additional software is installed, update management data for the additional software is generated. When the update management data for the additional software is attached to the additional software in advance, that data is used. If the update management data is not attached, cycles for confirming the presence of updates and the like are determined based on the nature of the software, and the update management data is thus generated. Then, the generated update management data is set in an update management table. The presence of software updates is checked for based on the cycles for confirming the presence of updates in the update management table.

CROSS REFERENCE TO RELATED APPLICATIONS

The present document claims priority to Japanese Priority DocumentJP2002-319128, filed in the Japanese Patent Office on Oct. 31, 2002, theentire contents of which are incorporated herein by reference to theextent permitted by law.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a software updating system, aninformation processing apparatus and method, a recording medium as wellas a program, and, more specifically, to a software updating system, aninformation processing apparatus and method, a recording medium as wellas a program that make it possible to appropriately supply data that isnecessary for updating software.

2. Description of the Related Art

There exists a service in which when software installed in a clientdevice is updated (for example, when a newer version is developed), thedeveloper of the software sends a notification via a network, andprovides, via a network, the client device with update data for updatingthe software in response to a request that is made based on thatnotification (see, for example, patent document 1).

[Patent Document 1]

Japanese Application Publication 2002-269272.

SUMMARY OF THE INVENTION

However, there is a problem where, because, ordinarily, multiplesoftware programs developed by a plurality of software developers areinstalled to client devices, if update data is not supplied as describedabove with respect to the software developed by some of thosedevelopers, client devices are unable to update those software programsappropriately.

The present invention addresses this issue, and seeks to allow theappropriate updating of software that a client device has.

A software updating system related to an embodiment of the presentinvention includes an electronic device and an update data supplyingapparatus. The electronic device is equipped with: acquisition means foracquiring update management data indicating the timing for confirmingthe presence of updates for installed software; storage means forstoring the update management data acquired by the acquisition means;judging means for judging based on the update management data whether ornot there exists, among the installed software, software for which it isnecessary that the presence of updates be confirmed; detection means fordetecting an update data supplying apparatus to which an inquiry is tobe made on the presence of updates for the software for which thejudging means has judged a confirmation to be necessary; inquiring meansfor making an inquiry on the presence of software updates to the updatedata supplying apparatus detected by the detection means; and executionmeans for executing a process based on update confirmation informationsupplied from the update data supplying apparatus in response to theinquiry by the inquiring means. The update data supplying apparatus isequipped with: confirmation means for confirming the presence or absenceof updates for the software regarding which there was an inquiry on thepresence of updates by the inquiring means of the electronic device; andsupplying means for supplying the update confirmation information to theelectronic device in accordance with a confirmation result by theconfirmation means.

The update confirmation information may be update data for updating thesoftware, or it may be information indicating the presence or absence ofupdates.

The update management data is attached to the installed software, andthe acquisition means of the electronic device is capable of acquiringthe attached update management data from the installed software.

The acquisition means of the electronic device is also capable ofacquiring update management data from the software developer of theinstalled software.

In the software updating system related to the present inventiondescribed above, on the electronic device's end, the update managementdata indicating the timing for confirming the presence of updates forthe installed software is acquired, the acquired update management datais stored, it is judged based on the update management data whether,among the installed software, there exists software for which aconfirmation on the presence of updates is necessary, the update datasupplying apparatus to which an inquiry is to be made on the presence ofupdates for the software for which it is judged that a confirmation isnecessary is detected, an inquiry is made to the detected update datasupplying apparatus on the presence of software updates, and a processbased on the update confirmation information supplied from the updatedata supplying apparatus in response to the inquiry is executed. On theupdate data supplying apparatus's end, the presence or absence ofupdates for the software regarding which an inquiry on the presence ofupdates was made is confirmed, and update confirmation information inaccordance with the confirmation result is supplied to the electronicdevice.

An information processing apparatus related to an embodiment of thepresent invention is equipped with: acquisition means for acquiringupdate management data indicating the timing for confirming the presenceof updates for installed software; storage means for storing the updatemanagement data acquired by the acquisition means; judging means forjudging based on the update management data whether or not there exists,among the installed software, software for which it is necessary thatthe presence of updates be confirmed; detection means for detecting anupdate data supplying apparatus to which an inquiry is to be made on thepresence of updates for the software for which the judging means hasjudged a confirmation to be necessary; inquiring means for making aninquiry on the presence of software updates to the update data supplyingapparatus detected by the detection means; and execution means forexecuting a process based on update confirmation information suppliedfrom the update data supplying apparatus in response to the inquiry bythe inquiring means.

An information processing method related to an embodiment of the presentinvention includes: an acquisition step for acquiring update managementdata indicating the timing for confirming the presence of updates forinstalled software; a storing step for storing the update managementdata acquired in the acquisition step; a judging step for judging basedon the update management data whether, among the installed software,there exists software for which the presence of updates needs to beconfirmed; a detection step for detecting an update data supplyingapparatus to which an inquiry is to be made on the presence of updatesfor the software for which a confirmation is judged to be necessary inthe judging step; inquiring step for making an inquiry on softwareupdates to the update data supplying apparatus detected in the detectionstep; and an execution step for executing a process based on updateconfirmation information supplied from the update data supplyingapparatus in response to the inquiry made in the inquiring step.

A program in a recording medium related to an embodiment of the presentinvention includes: an acquisition control step for controlling theacquisition of update management data indicating the timing forconfirming the presence of updates for installed software; a storagecontrol step for controlling the storing of the update management dataacquired in the acquisition control step; a judgment control step forcontrolling a judgment based on the update management data as to whetherthere exists, among the installed software, software for which thepresence of updates needs to be confirmed; a detection control step forcontrolling the detecting of an update data supplying apparatus to whichan inquiry is to be made on the presence of updates for the software forwhich a confirmation is judged to be necessary in the judgment controlstep; an inquiry control step for controlling the making of an inquiryon the presence of software updates to the update data supplyingapparatus detected in the detection control step; and an executioncontrol step for controlling the execution of a process based on updateconfirmation information supplied from the update data supplyingapparatus in response to the inquiry made in the inquiry control step.

A program related to an embodiment of the present invention makes acomputer execute a process including: an acquisition control step forcontrolling the acquisition of update management data indicating thetiming for confirming the presence of updates for installed software; astorage control step for controlling the storing of the updatemanagement data acquired in the acquisition control step; a judgmentcontrol step for controlling a judgment based on the update managementdata as to whether there exists, among the installed software, softwarefor which the presence of updates needs to be confirmed; a detectioncontrol step for controlling the detecting of an update data supplyingapparatus to which an inquiry is to be made on the presence of updatesfor the software for which a confirmation is judged to be necessary inthe judgment control step; an inquiry control step for controlling themaking of an inquiry on the presence of software updates to the updatedata supplying apparatus detected in the detection control step; and anexecution control step for controlling the execution of a process basedon update confirmation information supplied from the update datasupplying apparatus in response to the inquiry made in the inquirycontrol step.

In embodiments of the information processing apparatus and method aswell as the program related to the present invention, update managementdata indicating the timing for confirming the presence of updates forthe installed software is acquired, the acquired update management datais stored, it is judged based on the update management data whether,among the installed software, there exists software for which thepresence of updates needs to be confirmed, an update data supplyingapparatus to which an inquiry is to be made on the presence of updatesfor the software for which it is judged that a confirmation is necessaryis detected, an inquiry is made to the detected update data supplyingapparatus on the presence of software updates, and a process based onupdate confirmation information supplied from the update data supplyingapparatus in response to the inquiry is executed.

According to the present invention, it is possible to update software ina desirable manner.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram showing a configuration example of a softwareupdating system to which the present invention is applied;

FIG. 2 is a flowchart illustrating an outline of an update datasupplying service;

FIG. 3 is a diagram showing an example of a display showing the contentsof an update management table;

FIG. 4 is a diagram showing an update management table;

FIG. 5 is a block diagram showing a configuration example of the CEdevice in FIG. 1;

FIG. 6 is a block diagram showing a configuration example of the updatedata supplying server in FIG. 1;

FIG. 7 is a flowchart illustrating a process during the manufacture ofthe CE device in FIG. 1;

FIG. 8 is a flowchart illustrating a process for generating a devicecustomer registration code;

FIG. 9 is a flowchart illustrating a process for registering the updatedata supplying server in FIG. 1 with an authentication agent server;

FIG. 10 is a flowchart illustrating a process for registering the CEdevice in FIG. 1 with an authentication agent server;

FIG. 11 is a diagram showing an example of an input form for userinformation for authentication;

FIG. 12 is a diagram showing an example of a confirmation display foruser information for authentication;

FIG. 13 is a flowchart illustrating a process for registering the CEdevice in FIG. 1 with the update data supplying server;

FIG. 14 is a flowchart illustrating a procedure for using an update datasupplying service;

FIG. 15 is a flowchart showing a procedure for setting update managementdata in an update management table;

FIG. 16 is a diagram showing an example display showing the contents ofanother update management table;

FIG. 17 is a diagram showing the other update management table;

FIG. 18 is a diagram showing a configuration example of another softwareupdating system to which the present invention is applied;

FIG. 19 is a flowchart illustrating the operation of the home server inFIG. 18; and

FIG. 20 is a diagram illustrating a method of supplying update data.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 1 shows a configuration example of a software updating system towhich the present invention is applied. CE (consumer electronics) device1 through CE device manufacturer 4 are connected to a network 5, whichincludes the Internet.

The CE device 1 includes household appliances such as personalcomputers, mobile information terminal apparatuses, televisionreceivers, audio players, video players, car navigation apparatuses,microwave ovens, refrigerators, washing machines and the like, and hasnetwork functions for connecting to the network 5.

The CE device 1 has installed thereto various software for whichdistinct software developers supply update data, and performs variousfunctions using such software.

For each of the installed software programs, the CE device 1 makes aninquiry to an update data supplying server 3 on the presence of updatestherefor in a predetermined timing, and receives update data and thelike as needed. In so doing, the CE device 1 needs to be authenticatedby an authentication agent server 2 based on predeterminedauthentication information such as a device ID or the like. In otherwords, unless authenticated by the authentication agent server 2, the CEdevice 1 cannot use the update data supplying service provided by theupdate data supplying server 3.

The authentication agent server 2, in place of the update data supplyingserver 3, authenticates the CE device 1 requesting to use the updatedata supplying service.

The plurality of update data supplying servers 3-1, 3-2 and so on(unless it is necessary to identify the update data supplying serversindividually, they will be referred to as update data supplying servers3 for simplicity) supply, for example, update data for updating softwareto the CE device 1 in response to an inquiry if the CE device 1 isauthenticated by the authentication agent server 2.

The CE device manufacturer 4 manufactures the CE device 1 during whichit stores in the CE device 1 an update management table (describedlater) indicating inquiry cycles for making inquiries on updates for theinstalled software, authentication information, and the like.

It is to be noted that, hereinafter, for purposes of brevity, thetransmission and reception of data, information or the like performedvia, for example, the network 5 will be described simply astransmission/reception, abbreviating mention of “via the network 5.”

An outline of the update data supplying service will be described withreference to the flowchart in FIG. 2.

In step S1, the CE device 1 judges whether or not it is necessary toconfirm the presence of updates for all of the installed software, whichin this example would be the software programs that come bundled withthe CE device 1.

In this example, as shown in FIG. 3, if a user has checked a checkboxthat is displayed on a display section 47 (FIG. 5) of the CE device 1and which indicates all software programs are to have software updatestherefor confirmed when the power is turned on, when the power of the CEdevice 1 is turned on, it is judged that all of the software needs tohave the presence of update data confirmed. In addition, besides theexample of FIG. 3, it may be made possible to set a predetermined time,for example, so that it is judged necessary to confirm the presence ofupdates for all software when it is that time. A drawing illustratingthis example, however, is omitted.

Referring back to FIG. 2, if, in step S1, it is judged that confirmationfor all software is unnecessary, the process proceeds to step S2 wherethe CE device 1 references an update management table (FIG. 4) storedtherein, and judges whether there exists software for which the presenceof updates needs to be confirmed. If it is judged that such softwaredoes exist, the process proceeds to step S3.

In the example shown in FIG. 4, the names, IDs, version numbers, cyclesfor confirming the presence of software updates, and the contactinformation for making inquiries on software updates (URLs of the updatedata supplying servers 3) for the bundled software are included in theupdate management table. Hereinafter, such data will be referred to asupdate management data.

In the example shown in FIG. 4, every day, at the point it is determinedthat 10:00 has passed (for example, when the built-in timer isindicating a time later than 10:00), because the presence of updates forsoftware A needs to be confirmed, in step S2, a positive judgment ismade. Similarly, every Monday, at the point it is determined that 11:00has passed, or on the first day of every month, at the point it isdetermined that 12:00 has passed, because the presence of updates forsoftware B or software C, respectively, needs to be confirmed, apositive judgment is made in step S2.

The display 47A shown in FIG. 3 is for presenting the contents of theupdate management table in FIG. 4 to a user.

Referring back to FIG. 2, in step S3, with respect to the software forwhich it is determined that the presence of updates needs to beconfirmed, the URL of the update data supplying server to which aninquiry on the presence of updates is to be made is detected from theupdate management table by the CE device 1.

If it is judged, in step S1, that confirmation is necessary for allsoftware, the process proceeds to step S4, and the CE device 1 detectsfrom the update management table the URLs of all the update datasupplying servers 3 set therein.

Once the URL(s) of the update data supplying server(s) 3 is/are detectedin step S3 or step S4, the process proceeds to step S5, and anauthentication process with regard to the CE device 1 is performed.Details of this process will be described later.

Once the CE device 1 is authenticated in step S5, in step S6, the updatesupplying server 3, if needed, transmits update data for updatingsoftware, or transmits information indicating the presence or absence ofupdates (hereinafter, such information will be referred to as updateconfirmation information where appropriate) to the CE device 1. The CEdevice 1 executes a process based on the update confirmation informationfrom the update data supplying server 3. Details of this process, too,will be described later together with details of the process in step S5.

Such a process as described above is executed repeatedly in apredetermined timing.

FIG. 5 shows a configuration example of the CE device 1.

A CPU 41 executes various processes in accordance with software loadedto a RAM 43 from a ROM 42 or a storage section 48. Data that the CPU 41needs in executing various processes is also stored in the RAM 43 asrequired.

The CPU 41, the ROM 42 and the RAM 43 are interconnected via a bus 44.An input/output interface 45 is also connected to this bus 44.

An input section 46 including a keyboard, a mouse or the like, an outputsection 47 including a display such as a CRT (cathode ray tube), an LCD(liquid crystal display) or the like, and speakers, a storage section48, a communication section 49 including a modem, a terminal adaptor orthe like are connected to the input/output interface 45. Besidessoftware to be run by the CPU 41, the update management table,authentication information and the like mentioned above are also storedin the storage section 48. The communication section 49 performscommunication processes via the network 5.

As deemed necessary, a drive 50 is also connected to the input/outputinterface 45, and a magnetic disk 61, an optical disc 62, amagneto-optical disc 63, a memory card 64, or the like is loaded intothe drive 50 as needed. Computer programs read from such media may beinstalled to the memory section 48 as required.

FIG. 6 shows a configuration example of the update data supplying server3. Since its configuration is essentially similar to the configurationof the CE device 1, a detailed description thereof will herein beomitted.

Next a process during manufacture of the CE device 1 will be describedwith reference to the flowchart in FIG. 7.

The authentication agent server 2, in step S21, generates a randomnumber (hereinafter referred to as a pass phrase) which cannot bedeciphered by the user and a device ID for the CE device 1. In step S22,the authentication agent server 2 generates and stores a challengepublic key and a challenge secret key.

In step S23, the authentication agent server 2 transmits the device ID,the pass phrase and the challenge public key to the CE devicemanufacturer 4.

Once the CE device manufacturer 4 receives the device ID, the passphrase and the challenge public key from the authentication agent server2 in step S11, the CE device manufacturer 4, in step S12, generates adevice customer registration code from the device ID through a proceduresuch as the one shown in the flowchart in FIG. 8.

If the device ID is a 4-digit numerical sequence, in step S31 (FIG. 8),the sum of the numbers constituting each digit of the device ID isdivided by 9, and the remainder is inserted between the second and thirddigits of the device ID.

For example, if the device ID is “1234,” the sum of all the digits in“1234,” which is 10, is divided by 9. The remainder, which is 1, isinserted between the second digit “2” and the third digit “3,” and thenumerical sequence “12134” is generated.

Next, in step S32, the first digit and the fifth digit of the numericalsequence generated in step S31 are switched.

For example, the first digit “1” of the numerical sequence “12134” andthe fifth digit “4” are switched, and the numerical sequence “42131” isthereby generated.

In step S33, the sum of all the digits in the numerical sequencegenerated in step S32 is multiplied by 2, and the first digit of theproduct thus calculated is inserted between the fourth digit and thefifth digit of the numerical sequence generated in step S32. Thenumerical sequence thus obtained is taken to be the device customerregistration code.

For example, the sum of all the digits in the numerical sequence“42131,” which is 11, is multiplied by 2, which gives 22. The firstdigit of the product thus obtained, which is 2, is inserted between thefourth digit “3” of the numerical sequence “42131” and the fifth digit“1,” and the device customer registration code “421321” is thusgenerated.

Referring back to FIG. 7, in step S13, the CE device manufacturer 4stores the device ID, the pass phrase, and the challenge public keyreceived in step S11 in the storage section 48 of the CE device 1. TheCE device manufacturer 4 also stores the update management table (FIG.4), in which the update management data for the software bundled withthe CE device 1 is set, in the storage section 48. The CE devicemanufacturer 4 thus manufactures the CE device 1 storing predetermineddata in the storage section 48, and packages it with a sticker or thelike on which the device customer registration code generated in stepS12 is printed.

The CE device manufacturer 4 may also divide the information forauthentication into several parts and store them in different regions ofthe storage section 48. By so doing, tampering by malicious thirdparties can be prevented.

In step S14, the CE device manufacturer 4 stores information regardingthe CE device 1 (hereinafter referred to as device information) such asthe device ID, pass phrase, model code indicating the model of the CEdevice 1, date of manufacture and the like, and generates a deviceregistration master 4A which is a database.

In step S15, the CE device manufacturer 4 transmits the deviceregistration master 4A generated in step S14 to the authentication agentserver 2 via the network 5. The authentication agent server 2, in stepS24, stores the device registration master 4A for the CE device 1transmitted from the CE device manufacturer 4.

In transmitting the device registration master 4A to the authenticationagent server 2, the CE device manufacturer 4 encrypts the deviceregistration master 4A by some predetermined means and transmits it tothe authentication agent server 2 in order to prevent the deviceregistration master 4A from being intercepted by third parties. Inaddition, it is assumed that information handled between the CE device1, the authentication server 2 and the update data supplying server(s) 3is also encrypted by some predetermined means as deemed appropriate.

In step S16, sales of the CE device 1 are started. For example, the CEdevice 1 may be sold over the network 5.

The CE device 1 is thus manufactured.

Next, a process for registering the update data supplying service withthe authentication agent server 2 so that with respect to the updatedata supplying service provided by the update data supplying server 3(the service in which update data or the like is supplied to the CEdevice 1 in response to an inquiry on the presence of software updates),the authentication agent server 2 may, in place of (i.e., as asubstitute for) the update data supplying server 3, authenticate the CEdevice 1 will be described with reference to the flowchart in FIG. 9.

In step S51, the update data supplying server 3 requests registration ofsubstitute authentication for the update data supplying service to theauthentication agent server 2.

In step S41, the authentication agent server 2 examines the update datasupplying server 3, and in step S42, based on the result of theexamination, the authentication agent server 2 judges whether the updatedata supplying service can be registered as a service for which it canperform authentication. If it is judged that the service cannot beregistered, the following steps S43 and S44, which will be describedlater, are skipped, and the process is terminated.

On the other hand, if, in step S42, it is judged that the update datasupplying service can be registered, in step S43, the authenticationagent server 2 stores the URL or the like of the update data supplyingserver 3 which requested registration of the update data supplyingservice. Then, in step S44, the authentication agent server 2 generatesinformation in which the URL or the like of the authentication agentserver 2 is included (hereinafter referred to as authentication agentserver confirmation information), and transmits it to the update datasupplying server 3.

In step S52, the update data supplying server 3 judges whether or notthe authentication agent server confirmation information has beenreceived, and if not (in other words, if a negative judgment was made instep S42 by the authentication agent server 2, step S44 was notperformed and the authentication agent server confirmation informationwas not transmitted), the process is terminated.

In step S52, if it is judged that the authentication agent serverconfirmation information has been received, the update data supplyingserver 3, in step S53, saves the authentication agent serverconfirmation information.

Thus, the update data supplying service is registered with theauthentication agent server 2 as a service for which authentication byproxy (substitute authentication) can be performed.

Next, a process for registering the CE device 1 with the authenticationagent server 2 so that the authentication agent server 2 mayauthenticate the CE device 1 with respect to the update data supplyingservice registered in the manner described above will be described withreference to the flowchart in FIG. 10.

In step S61, when the user who has purchased the CE device 1 runs aregistration application for the CE device 1 (for example, a browser, ora dedicated application for registering the CE device), the CE device 1performs a process for obtaining user information.

For example, the CE device 1 may display on a display of the outputsection 47 an input form, as shown in FIG. 11, for entering userinformation such as the user's name, address, telephone number, as wellas, for example, zip-code, date of birth, sex, type of credit card,credit card number and expiration date and the like (hereinafterreferred to as user information for authentication). In the exampleshown in FIG. 11, because the device ID is stored in the CE device 1(step S13 in FIG. 7), the device ID is already displayed in the inputform.

After the user has entered the user information for authentication inthe input form of FIG. 11, the user hits a confirm button 47B to havethe information just entered displayed as in FIG. 12. When the user hitsthe register button 47C, the CE device 1 obtains the information enteredin the input form in FIG. 11 as the user information for authenticationfor that user.

Referring back to FIG. 10, in step S62, the CE device 1 transmits theuser information for authentication obtained in step S61 along with thedevice ID and pass phrase stored in the storage section 48 (step S13 inFIG. 7) to the authentication agent server 2.

In step S71, the authentication agent server 2 receives the userinformation for authentication, the device ID, and the pass phrasetransmitted from the CE device 1. In step S72, the authentication agentserver 2 checks if a device registration master 4A (step S24 in FIG. 7)in which the received device ID and pass phrase are registered exists inorder to judge whether the CE device 1 is a device that is authentic(legitimate).

If, in step S72, it is judged that the CE device 1 is a legitimatedevice, in other words, if a device registration master 4A in which thedevice ID and pass phrase received in step S71 are registered exists,the authentication agent server 2, in step S73, registers the userinformation for authentication received in step S71 in association withthe device ID registered in the device registration master 4A, andstores a customer registration master 2A thus generated. Thus, theauthentication agent server 2 is able to search for device informationas well as user information for identification based on the device ID.

In step S74, the authentication agent server 2 notifies the CE device 1that registration is complete.

In step S72, if it is judged that the CE device 1 is not a legitimatedevice, in step S75, the CE device 1 is notified of the fact thatregistration could not be completed.

Once a notification message is given in step S74 or step S75, theauthentication agent server 2 terminates the process.

In step S63, the CE device 1 receives a notification from theauthentication agent server 2 indicating that either registration iscomplete or registration could not be completed, and displays a messagecorresponding to the notification. The process is then terminated.

Thus, the CE device 1 is (or is not) registered with the authenticationagent server 2 as a device that can be authenticated.

Next, a process for registering the CE device 1 with the update datasupplying server 3 so that the CE device 1 may use the update datasupplying service will be described with reference to the flowchart inFIG. 13.

In step S91, the update data supplying server 3 makes a request to theCE device 1 for user information for service registration.

In step S81, the CE device 1 displays on the output section 47 an inputform for entering a device customer registration code in order to obtainthe device customer registration code, and displays an input form forentering user information for service registration in order to obtainthe user information for service registration. In step S82, the obtaineduser information and device customer registration code is transmitted tothe update data supplying server 3.

In step S92, the update data supplying server 3 transmits to theauthentication agent server 2 the device customer registration codetransmitted from the CE device 1, and requests that the device ID of theCE device 1 be supplied.

In step S101, the authentication computes the device ID from the devicecustomer registration code transmitted from the update data supplyingserver 3. Since the device customer registration code is derived througha computation based on the device ID as described with reference to theflowchart in FIG. 8, by performing an inverse computation on the devicecustomer registration code, the device ID can be computed.

In step S102, the authentication agent server 2 transmits the computeddevice ID to the update data supplying server 3.

In step S93, the update data supplying server 3 registers the userinformation from the CE device 1 in association with the device ID fromthe authentication agent server 2, and stores a customer registrationmaster 3A thus generated. Thus, the update data supplying server 3 iscapable of searching for user information based on the device ID.

Thus, the CE device 1 is registered with the update data supplyingserver 3.

Next, operations of the CE device 1, the authentication agent server 2,and the update data supplying server 3 when the CE device 1 uses theupdate data supplying service will be described with reference to theflowchart in FIG. 14. In other words, steps S151 through S157 by the CEdevice 1, steps S171 through S177 by the update data supplying server 3,and steps S191 through S197 by the authentication agent server 2 in FIG.14 correspond to the process in step S5 in FIG. 2, and steps S158 andS159 by the CE device 1, and step S178 by the update data supplyingserver 3 correspond to the process in step S6 in FIG. 2.

When the update data supplying server 3 to which an inquiry on thepresence of software updates is to be made is detected in step S3 orstep S4 in FIG. 2, the CE device 1, in step S151, transmits to theupdate data supplying server 3 the ID and version number, for example,of the software for which the presence of updates is to be confirmed,and makes an inquiry on the presence of updates for that software(requests the use of the update data supplying service). In FIG. 14,although only a process of the CE device 1 with respect to a singleupdate data supplying server 3, and a process of a single update datasupplying server 3 are indicated, if a plurality of the update datasupplying servers 3 are detected in step S3 or step S4, the CE device 1performs a process similar to the process shown in FIG. 14 with respectto each of the detected update data supplying servers 3, and a processsimilar to the process shown in FIG. 14 is performed by each of theupdate data supplying servers 3.

When the use of the update data supplying service is requested by the CEdevice 1, the update data supplying server 3, in step S171, judgeswhether or not a session is established between itself and the CE device1. If it is judged that a session is established with the CE device 1,steps S172 through S177, which will be described later, are skipped, andthe process proceeds to step S178.

On the other hand, if in step S171, it is judged that a session is notestablished, the update data supplying server 3, in step S172, transmitsthe authentication agent server confirmation information stored in stepS53 in FIG. 9 to the CE device 1.

In step S152, the CE device 1 judges whether or not the authenticationagent server confirmation information has been received from the updatedata supplying server 3, and if it is judged that it has not beenreceived (in other words, if a positive judgment was made in step S171by the update data supplying server 3, step S172 was not performed andthe authentication agent server confirmation information was nottransmitted), steps S153 through S157, which will be described later,are skipped and the process proceeds to step S158.

On the other hand, if, in step S152, it is judged that theauthentication agent server confirmation information has been received,the CE device 1, in step S153, performs a process of confirming whetherthe authentication agent server 2 is the proper server using the URLincluded in the received authentication agent server confirmationinformation.

For example, the CE device 1 generates a random number (hereinafter therandom number generated here will be referred to as a challenge whereappropriate), and this random number (challenge) is transmitted to thesite of the URL (the authentication agent server 2) embedded in theauthentication agent server confirmation information.

The authentication agent server 2 encrypts the random number (challenge)from the CE device 1 using the challenge secret key generated in stepS22 in FIG. 7, and transmits it to the CE device 1.

Using the challenge public key stored in the storage section 48 in stepS13 in FIG. 7, the CE device 1 decrypts the random number (challenge)that is encrypted with the challenge secret key and is transmitted fromthe authentication agent server 2, and matches it against the challengegenerated earlier. If both challenges do match, it is identified thatthe authentication agent server 2 is the proper server.

In step S154, the CE device 1, based on the confirmation result of stepS153, judges whether the authentication agent server 2 is the properserver. If it is judged not to be the proper server, steps S155 throughS159, which will be described later, are skipped, and the process isterminated.

On the other hand, if, in step S154, it is judged that theauthentication agent server 2 is the proper server, the CE device 1, instep S155, transmits to the authentication agent server 2 the device IDand the pass phrase stored in the storage section 48 in step S13 in FIG.7, as well as the URL of the update data supplying server 3 detected instep S3 or step S4 in FIG. 2, thus requesting authentication in order touse the update data supplying service.

After performing the process that corresponds to the authenticationagent server confirmation process at the CE device 1 (step S153) in stepS191, the authentication agent server 2, in step S192, judges whether ornot authentication has been requested from the CE device 1. If it isjudged that authentication has not been requested (if a negativejudgment was made in step S154 at the CE device 1, step S155 was notperformed, and authentication was not requested), steps S193 throughsteps S197, which will be described later, are skipped and the processis terminated.

On the other hand, if, in step S192, it is judged that authenticationhas been requested by the CE device 1, the authentication agent server2, in step S193, judges whether or not the update data supplyingservice, which the CE device 1 is requesting to use, is registered as aservice for which the authentication agent server 2 is capable ofperforming authentication by proxy. Specifically, since the URL(s) ofthe update data supplying server(s) 3 is/are stored in step S43 in FIG.9, the authentication agent server 2 judges whether or not the same URLas the one transmitted from the CE device 1 is stored.

In step S193, if it is judged that the update data supplying service isregistered, the authentication agent server 2, in step S194, checks if adevice registration master 4A in which the device ID and pass phrasereceived in step S192 are registered exists, and thus authenticates theCE device 1 (authentication by proxy is performed).

In step S193, if it is judged that the update data supplying service isnot registered, or if in step S194, the CE device 1 cannot beauthenticated, steps S195 through S197, which will be described later,are skipped and the process is terminated.

Once the CE device 1 is authenticated in step S194, the authenticationagent server 2, in step S195, issues a one-time ID for identifying theCE device 1 until it is invalidated in step S196, which will bedescribed later, and transmits it to the CE device 1.

In step S156, the CE device 1 judges whether or not the one-time ID fromthe authentication agent server 2 has been received. If it is judgedthat it has not been received (in other words, if a negative judgment ismade at the authentication agent server 2 in step S193 or step S194,step S195 is not performed, and the one-time ID is not transmitted),steps S157 through S159, which will be described later, are skipped, andthe process is terminated.

On the other hand, if, in step S156, it is judged that the one-time IDhas been received, the CE device 1, in step S157, transmits the one-timeID received in step S156 to the update data supplying server 3.

In step S173, the update data supplying server 3 judges whether or notthe one-time ID from the CE device 1 has been received. If it is judgedthat it has not been received (in other words, if a negative judgment ismade in step S156 at the CE device 1, step S157 is not performed, andthe one-time ID is not transmitted), steps S174 through S178, which willbe described later, are skipped, and the process is terminated.

On the other hand, if, in step S173, it is judged that the one-time IDhas been received, the update data supplying server 3, in step S174,transmits the one-time ID received in step S173 to the authenticationagent server 2, and requests the provision of the device information onthe CE device 1.

In step S196, the authentication agent server 2 receives the one-time IDtransmitted from the update data supplying server 3, and confirmswhether or not the one-time ID is transmitted from the servercorresponding to the URL received in step S192. The one-time ID thenbecomes invalid.

In step S197, the authentication agent server 2 searches the deviceregistration master 4A of the CE device 1 for the device information(including the device ID) on the CE device 1 identified by the one-timeID received in step S196, and transmits it to the update data supplyingserver 3.

Once, in step S175, the update data supplying server 3 receives thedevice information on the CE device 1 transmitted from theauthentication agent server 2, it is judged, in step S176, whether ornot the CE device 1 is registered with the update data supplying server3 as a device that can use the update data supplying service. Forexample, since, in step S93 in FIG. 13, the customer registration master3A in which the device ID of the CE device 1 is registered is stored,the update data supplying server 3 judges whether or not a customerregistration master 3A in which the device ID transmitted from theauthentication agent server 2 is registered is stored.

In step S176, if it is judged that the CE device 1 is not registered,steps S177 and S178, which will be described later, are skipped and theprocess is terminated.

On the other hand, if, in step S176, it is judged that the CE device 1is registered, the update data supplying server 3, in step S177,establishes a session with the CE device 1. While the session iscontinued with the CE device 1, generally, authentication of the CEdevice 1 is not requested to the authentication agent server 2 (in otherwords, a positive judgment is made in step S171, and steps S172 throughS176 are skipped).

When it is judged in step S171 that a session is established, or when asession is established in step S177, the update data supplying server 3,in step S178, confirms whether or not the software regarding which aninquiry is made by the CE device 1 has been updated, and transmits tothe CE device 1 the update confirmation information in accordance withthe confirmation result. For example, if the software has been updated,update data for updating the software that the CE device 1 has may betransmitted to the CE device 1. In addition, information indicating thepresence or absence of updates may be transmitted to the CE device 1.

When it is judged, in step S152, that the authentication agent serverconfirmation information has not been received (when there is apossibility that a session is already established), or if, in step S157,the one-time ID is transmitted to the authentication agent server 2, theCE device 1, in step S158, judges whether or not the update confirmationinformation from the update data supplying server 3 has been received.If it is judged that it has not been received (in other words, if anegative judgment is made in step S176 at the update data supplyingserver 3, step S178 is not performed, and the update data is nottransmitted), the process is terminated.

On the other hand, if, in step S158, it is judged that the updateconfirmation information from the update data supplying server 3 hasbeen received, the CE device 1, in step S159, performs a process inaccordance with the received update confirmation information. Forexample, if the update data is received, the software is updatedaccordingly. Alternatively, if information indicating the presence orabsence of updates is received, the CE device 1 displays information inaccordance therewith on the output section 47, and performs a process inaccordance with instructions from the user made with respect to thedisplayed information (for example, a process for obtaining update datamay be performed).

Thus, the CE device 1 is able to update installed softwareappropriately.

In the description above, the CE device 1 makes an inquiry on thepresence of updates when the update data supplying server 3 is detectedin step S3 or step S4 in FIG. 2. However, the inquiry may be postponedtill a predetermined time late at night during which traffic in thenetwork 5 is lighter.

In addition, the CE device 1 may prioritize inquiries for some softwareon the presence of updates depending on the importance of the software.For example, if the timings for making inquiries on update data coincidebetween security related software and some other software, inquiries onthe presence of updates for the security related software may beprioritized over those of the other software

In the description above, the example was of a case where bundledsoftware was updated. However, with respect to software that isinstalled later (hereinafter referred to as additional software), too,by additionally setting the update management data for the additionalsoftware in the update management table, the additional software may beupdated appropriately.

FIG. 15 shows a procedure for additionally setting the update managementdata for the additional software in the update management table. Whenthe additional software is installed in step S201, the CE device 1, instep S202, generates the update management data for the additionalsoftware.

If the update management data for the additional software is providedalong with the additional software, the data may be used. If the updatemanagement data is not provided with the additional software, cycles forconfirming the presence of updates may be decided on depending on thenature of the software, and the update management data may be generated.For example, for security related software, the confirmation cycle maybe made shorter. In addition, the update management data may be obtainedfrom the developer of the additional software.

In step S203, the CE device 1 sets the generated update management datain the update management table.

FIG. 16 shows the update management data in FIG. 4 in a state where theupdate management data for software D is set additionally. In addition,FIG. 17 shows an example of a display 47A that displays the contents ofthe update management table of FIG. 16.

In the description above, an example was given where the CE device 1communicates directly with the authentication agent server 2 and theupdate data supplying server 3 via the network 5. However, as shown inFIG. 18, communications may be performed with the authentication agentserver 2 and the update data supplying server 3 via a home server 101connected to the network 5.

In this example, in step S5 in FIG. 2, the URL of the update datasupplying server 3 detected in a process corresponding to step S3 orstep S4 is notified to the home server 101 from the CE device 1connected thereto (a plurality of the CE devices 1 may also beconnected). Then, in a process corresponding to step S151 in FIG. 14,the home server 101 accesses the update data supplying server 3 usingthe notified URL, and makes an inquiry on the presence of softwareupdates. Then, processes corresponding to steps S152 through S158 areperformed.

A process corresponding to step S159 is performed in a procedureillustrated with the flowchart of FIG. 19.

When the update confirmation information supplied from the update datasupplying server 3 (step S158 in FIG. 14) is received, the home server101, in step S221, notifies all of the CE devices 1 connected theretoaccordingly.

In step S211, the CE device 1 judges whether or not it has been notifiedthat the update confirmation information has been received. In FIG. 19,for purposes of brevity, a process by the home server 101 in relation toa single CE device 1 and a process of a single CE device 1 are shown.However, in reality, the home server 101 performs a process similar tothe process shown in FIG. 19 with respect to each of the connected CEdevices 1, and each of the CE devices 1 also performs a process similarto the process shown in FIG. 19.

In step S211, if it is judged that it has been notified that the updateconfirmation information has been received, the CE device 1, in stepS212, judges whether or not the update confirmation information is fromthe update data supplying server 3 detected in step S3 or step S4 inFIG. 2. If judged so, the process proceeds to step S213.

In step S213, the CE device 1 requests the provision of the receivedupdate confirmation information to the home server 101.

In step S222, the home server 101 judges whether or not the CE device 1has requested the provision of the update confirmation information. Ifit is judged that there has been a request, the home server 101, in stepS223, supplies to the CE device 1 the update confirmation informationsupplied from the update data supplying server 3.

In step S214, the CE device 1 receives the update confirmationinformation supplied from the home server 101, and performs a processbased thereon.

In step S212, if it is judged that the update confirmation informationis not from the update data supplying server 3 to which an inquiry onthe presence of updates was made, the CE device 1, in step S215,notifies the home server 101 accordingly.

The CE device 1 terminates the process when it is judged, in step S211,that there has not been any notification that the update confirmationinformation from the home server 101 has been received, when apredetermined process is performed in step S214, or when a predeterminednotification is made in step S215.

The home server 101 terminates the process when it is judged, in stepS222, that there has been no request by the CE device 1, or when theupdate confirmation information is supplied to the CE device 1 in stepS223.

In addition, the home server 101, during a process corresponding to stepS151 in FIG. 14, may also postpone making inquiries until apredetermined time late at night at which the traffic in the network 5is not as heavy.

Further, although not mentioned in the description above, the updatedata supplied to the CE device 1 may also be stored in the update datasupplying server 3, or, as shown in FIG. 20, it may be obtained, asdeemed appropriate, from a software developer 201 via a network (such asthe network 5, for example).

Since the invention disclosed herein may be embodied in other specificforms without departing from the spirit or general characteristicsthereof, some of which forms have been indicated, the embodimentsdescribed herein are to be considered in all respects illustrative andnot restrictive. The scope of the invention is to be indicated by theappended claims, rather than by the foregoing description, and allchanges which come within the meaning and range of equivalents of theclaims are intended to be embraced therein.

1. A software updating system, comprising: an update data supplyingapparatus for supplying update confirmation information regarding thepresence or absence of updates for predetermined software via a network;an electronic device for executing a process in accordance with saidupdate confirmation information supplied from said update data supplyingapparatus, wherein said electronic device includes: generating means forgenerating update management data, the update management data indicatinga timing cycle based on a nature of installed software and forconfirming the presence of updates for the installed software, when theupdate management data is not provided with the installed software;storage means for storing said update management data generated by saidgenerating means; judging means for judging, based on said updatemanagement data whether or not, among said installed software, thereexists software for which a presence of updates needs to be confirmed;detection means for detecting said update data supplying apparatus towhich an inquiry is to be made on the presence of updates for saidsoftware for which said judging means has judged a confirmation to benecessary; inquiring means for making an inquiry on the presence ofupdates for said software to said update data supplying apparatusdetected by said detection means; and execution means for executing aprocess based on said update confirmation information supplied from saidupdate data supplying apparatus in response to said inquiry made by saidinquiring means, and said update data supplying apparatus includes:confirmation means for confirming the presence or absence of updates forsaid software regarding which there was an inquiry on the presence ofupdates by said inquiring means of said electronic device; and supplyingmeans for supplying to said electronic device said update confirmationinformation in accordance with a confirmation result by saidconfirmation means.
 2. The software updating system according to claim1, wherein said update confirmation information is one of update datafor updating said software and information indicating the presence orabsence of updates.
 3. An information processing method of aninformation processing apparatus which executes a process in accordancewith update confirmation information supplied from an update datasupplying apparatus that supplies via a network said update confirmationinformation regarding the presence or absence of updates forpredetermined software, comprising the steps of: generating updatemanagement data, the update management data indicating a timing cyclebased on a nature of installed software and for confirming the presenceof updates for the installed software, when the update management datais not provided with the installed software; storing said updatemanagement data generated in said generating step; judging, based onsaid update management data whether or not, among said installedsoftware, there exists software for which a presence of updates needs tobe confirmed; detecting said update data supplying apparatus to which aninquiry is to be made on the presence of updates for said software forwhich a confirmation has been judged to be necessary in said judgingstep; making an inquiry on the presence of updates for said software tosaid update data supplying apparatus detected in said detection step;and executing a process based on said update confirmation informationsupplied from said update data supplying apparatus in response to saidinquiry made in said step of making said inquiry.
 4. A recording mediumthat stores a computer readable program for an information processingapparatus which when executed causes the information processingapparatus to execute a process in accordance with update confirmationinformation supplied from an update data supplying apparatus thatsupplies, via a network, said update confirmation information regardingthe presence or absence of updates for predetermined software, saidprocess comprising steps of: generating update management data, theupdate management data indicating a timing cycle based on a nature ofinstalled software and for confirming the presence of updates for theinstalled software, when the update management data is not provided withthe installed software; storing said update management data generated insaid generating step; judging, based on said update management datawhether or not, among said installed software, there exists software forwhich a presence of updates needs to be confirmed; detecting said updatedata supplying apparatus to which an inquiry is to be made on thepresence of updates for said software for which a confirmation has beenjudged to be necessary in said judging step; making an inquiry on thepresence of updates for said software to said update data supplyingapparatus detected in said detection step; and executing a process basedon said update confirmation information supplied from said update datasupplying apparatus in response to said inquiry made in said step ofmaking said inquiry.
 5. A software updating system, comprising: anupdate data supplying apparatus configured to supply update confirmationinformation regarding the presence or absence of updates forpredetermined software via a network; an electronic device configured toexecute a process in accordance with said update confirmationinformation supplied from said update data supplying apparatus, whereinsaid electronic device includes: a generation unit configured togenerate update management data, the update management data indicating atiming cycle based on a nature of installed software and for confirmingthe presence of updates for the installed software, when the updatemanagement data is not provided with the installed software; a storageunit configured to store said update management data generated by saidgeneration unit; a judging unit configured to judge, based on saidupdate management data whether or not, among said installed software,there exists software for which a presence of updates needs to beconfirmed; a detection unit configured to detect said update datasupplying apparatus to which an inquiry is to be made on the presence ofupdates for said software for which said judging unit has judged aconfirmation to be necessary; a inquiry unit configured to make aninquiry on the presence of updates for said software to said update datasupplying apparatus detected by said detection unit; and an executionunit configured to execute a process based on said update confirmationinformation supplied from said update data supplying apparatus inresponse to said inquiry made by said inquiry unit, and said update datasupplying apparatus includes: a confirmation unit configured to confirmthe presence or absence of updates for said software regarding whichthere was an inquiry on the presence of updates by said inquiry unit ofsaid electronic device; and a supply unit configured to supply to saidelectronic device said update confirmation information in accordancewith a confirmation result by said confirmation unit.
 6. An electronicdevice for executing a process in accordance with update confirmationinformation regarding a presence or absence of updates for predeterminedsoftware supplied from an update data supplying apparatus via a network,wherein said electronic device comprises: generating means forgenerating update management data, the update management data indicatinga timing cycle based on a nature of the installed software and forconfirming the presence of updates for the installed software, when theupdate management data is not provided with installed software; storagemeans for storing said update management data generated by saidgenerating means; judging means for judging, based on said updatemanagement data whether or not, among said installed software, thereexists software for which a presence of updates needs to be confirmed;detection means for detecting said update data supplying apparatus towhich an inquiry is to be made on the presence of updates for saidsoftware for which said judging means has judged a confirmation to benecessary; inquiring means for making an inquiry on the presence ofupdates for said software to said update data supplying apparatusdetected by said detection means; and execution means for executing aprocess based on said update confirmation information supplied from saidupdate data supplying apparatus in response to said inquiry made by saidinquiring means.
 7. An information processing method of an informationprocessing apparatus which executes a process in accordance with updateconfirmation information supplied from an update data supplyingapparatus that supplies via a network said update confirmationinformation regarding the presence or absence of updates forpredetermined software, comprising the steps of: generating updatemanagement data, the update management data indicating a timing cyclebased on a nature of the installed software and for confirming thepresence of updates for the installed software, when the updatemanagement data is not provided with installed software; storing saidupdate management data generated by said generating; judging, based onsaid update management data whether or not, among said installedsoftware, there exists software for which a presence of updates needs tobe confirmed; detecting said update data supplying apparatus to which aninquiry is to be made on the presence of updates for said software forwhich said judging has judged a confirmation to be necessary; making aninquiry on the presence of updates for said software to said update datasupplying apparatus detected by said detecting; and executing a processbased on said update confirmation information supplied from said updatedata supplying apparatus in response to said inquiry made by saidinquiring.